Log files are useful for troubleshooting issues in web applications. The Alpha Anywhere Application Server for IIS writes events to the Xbasic Error log and Trace logs when abnormal conditions are encountered. The Application Server for IIS also writes to the Windows Event Logs. Failed Request Tracing can be used, as well, to track down failed requests.

Named AlphaDAO connection strings must be defined relative to the server in a publishing profile. The Application Server's Connection String Builder Genie can be used to create and test published connection strings. Connection strings can then be copied to the publishing profile in the Alpha Anywhere Development Environment.

The Classic Application Server allows for an alternate configuration file to be specified. This is done through the use of a command line option, CONFIGFILE. For example, to launch the Application Server using a configuration file named TestConfig.xml in the root of the server's C drive:

Step by step instructions for running multiple instances of the application server:

Traditionally, Application Server administrators provide service for multiple applications by using a single instance of the Application Server, placing each distinct application within a different subdirectory under the webroot.

Alpha Anywhere and the Application Server each store server settings in a configuration file on the computer's hard drive. The location of the file being used by an instance of Alpha Anywhere or the Application Server can be determined using the function *[xb:a5_GetAppServerConfigFile()]*. For example:

Multiple version of the Application Server for IIS can be installed on one system for a single license. This allows you to test new releases or deploy multiple applications running on different versions of Alpha Anywhere.

A step-by-step guide to configuring the Alpha Anywhere Application Server and publishing profile to publish your Alpha Anywhere Application using HTTP publish.